Soft goal

In ice hockey and Association Football, a soft goal can also refer to a goal that is the result of a weak effort, or none at all, and should have been a routine save by the goalkeeper and the other defending players.

The term soft goal is used in connection with modeling languages and specially with goal-oriented modeling. Soft goals are objectives that miss clear-cut criteria [1]. Soft goals can represent:

Non-functional requirements (or quality attributes, qualities, or more colloquially "-ilities") are global qualities of a software system, such as flexibility, maintainability, usability, and so forth. Such requirements are usually stated only informally; and they are often controversial (i.e. management wants a secure system but staff desires user-friendliness). They are also often difficult to validate.

Contents

Why soft?

Normally a goal is a very strict and clear logical criterion. It is satisfied when all sub-goals are satisfied. But in non-functional requirements you often need more loosely defined criteria, like satisficeable or unsatisficeable. The term satisficing was first coined by Herbert Simon. Soft goals are goals that do not have a clear-cut criterion for their satisfaction: they are satisficed when there is sufficient positive and little negative evidence for this claim, while they are unsatisficeable in the opposite case.

Relations between soft goals

References

  1. ^ S-Cube Knowledge Model: Soft Goals

See also

Mylopoulos John, Chung Lawrence, Yu Eric: From Object-Oriented to Goal-Oriented Requirements Analysis